[cmake] WIP#40253
Conversation
|
Also affecting D:\b\cmake\x64-windows-rel\bin\cmake.exe, i.e release config. |
|
The deployed |
| "name": "qtbase", | ||
| "default-features": false |
There was a problem hiding this comment.
that is probably wrong. needs at least widgets and gui
There was a problem hiding this comment.
True. And doesn't matter for CI. (What I really want is a feature, but it is not a priority.)
|
What is the link line for cmake.exe itself ?
With ADD_BIN_TO_PATH it should run just fine. I did this intentionally so that I am sure that the build cmake actually works without having to test it manually. |
CI logs:
I agree. However it fails, and I don't have a local msvc installation to investigate the difference. |
|
Release only triplet: No problem.... |
|
So it is only in CI, and only before app-local deployment? |
|
And did you pull in all transitive dependencies which are pulled in via test ports? For example, with curl, you also need vcpkg-ci-curl. Which got a number of additions recently. |
I only pulled in the minimal required deps. x64-windows this way also worked. I can test with more but in the end it is probably a release/debug problem. |
|
./vcpkg.exe install --overlay-ports=scripts/test_ports/ cmake vcpkg-ci-curl --host-triplet=x64-windows worked as expected |
|
Looking at the link line I would guess libarchive might be to blame if libcurl isnt the one to blame. |
|
Hmm building with libarchive[*] also works. |
|
#40224 passed CI now. The actual |
|
Most changes might still be useful. |
Adressing baseline regression: The Windows DLL triplets fail to build downstream cmake.
The link command is executed via the installed cmake (
D:\downloads\tools\cmake-3.29.2-windows\cmake-3.29.2-windows-i386\bin\cmake.exe),but the failing install command is executed via the the freshly built cmake (
D:\b\cmake\x64-windows-dbg\bin\cmake.exe).(From #40224 (comment)
CMake wants it this way for native builds:
https://github.com/Kitware/CMake/blob/4aa42149d69c8e0fa542e18196463d671190710c/Source/cmGlobalGenerator.cxx#L3121-L3127
So there seems to be an issue with DLLs.